Skip to content

chore: upgrade dependencies for week 09. Auto-generated by devCalc#1391

Merged
tj098895 merged 1 commit intomainfrom
upgrade_dependencies_week_09_2A12EF
Feb 23, 2026
Merged

chore: upgrade dependencies for week 09. Auto-generated by devCalc#1391
tj098895 merged 1 commit intomainfrom
upgrade_dependencies_week_09_2A12EF

Conversation

@krisolba1
Copy link
Copy Markdown
Contributor

Type of Work

  • Patch: X.Y.Z+1. NEGLIGIBLE visible changes, does not change input or output - OR changes behaviour. Use chore:, refactor: etc
  • Minor: X.Y+1.Z. Minor changes, might ADD new input (YAML), or other backwards-compatible changes. Use feat:, fix:
  • Major: X+1.Y.Z. Major and most likely BREAKING changes, wo. backwards compatibility, or removing temporary backwards compatibility functionality. Use ! or BREAKING:.

See here (internal): https://github.com/equinor/ecalc-internal/discussions/1044

Have you remembered and considered?

  • IF FEAT: I have remembered to update documentation
  • IF FIX OR FEAT: I have remembered to update manual changelog (docs/drafts/next.draft.md)
  • IF BREAKING: I have remembered to update migration guide (docs/docs/migration_guides/)
  • IF BREAKING: I have committed with BREAKING: in footer or ! in header
  • I have added tests (if not, comment why)
  • I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
  • I have included the Github issue nr in the footer!

What is this PR all about?

What else did you consider?

Between the lines?

@krisolba1 krisolba1 requested a review from a team as a code owner February 23, 2026 13:12
@tj098895
Copy link
Copy Markdown
Contributor

@Aleksander-Karlsson du som har testa denne GH actionen en del, har du oversikt over hva som skjer? Hver gang (nesten?) vi har oppdatering av deps, så feiler den med flere deps som tilsynelatende ikke har licenses den finner - betyr det at GH actionen er indeterministic? eller er det alle de som har oppdatert seg siden sist, og som den allerede ikke har funnet lisens til, som havner i delta for "nye lisenser å ta stilling til"? men, om vi legger de til, så feiler den omtrent emd en gang, at de plutselig ikke er på lista. bruker vi GH actionen feil?

@tj098895
Copy link
Copy Markdown
Contributor

Looking a bit more into the license thing, and found that:

  • seems that license is only checked on updated packages, and we do not have a baseline.
  • either the api is not working, or many of our packages are not listed in the api being used (clearlydefined.io)
  • the api, which consists of automatic data harvesting and user curated data seems to not be updated so much any more (numpy updated 5 years ago ...)

so, we might need to look for another solution, will check more closely. accepting and merging this PR, as it seems that it doesnt make a difference.

@tj098895 tj098895 merged commit c662c35 into main Feb 23, 2026
21 of 22 checks passed
@tj098895 tj098895 deleted the upgrade_dependencies_week_09_2A12EF branch February 23, 2026 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants